Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

trace: remove redundant bounds implied by the trait definition #363

Closed

Conversation

petrosagg
Copy link
Contributor

Many methods in DD are requiring the BatchReader and Cursor bounds on the Batch and Cursor associated types of a TraceReader respectively. However these bounds are already implied by the trait definition and can be omitted, resulting in simpler signatures.

Many methods in DD are requiring the BatchReader and Cursor bounds on
the Batch and Cursor associated types of a TraceReader respectively.
However these bounds are already implied by the trait definition and can
be omitted, resulting in simpler signatures.

Signed-off-by: Petros Angelatos <[email protected]>
@frankmcsherry
Copy link
Member

Did Rust land some implied_bounds work? These bounds have traditionally been there because Rust complains if they are not. If the world changed while I wasn't looking, hooray!

@petrosagg
Copy link
Contributor Author

Hm, I'm not sure. I haven't tried compiling with an older rust

@guswynn
Copy link
Contributor

guswynn commented Mar 30, 2022

implied_bounds is not landed, but it just started being worked on? rust-lang/rust#44491 (comment), i think thats just for struct bounds tho? associated type bounds might have always worked

@petrosagg
Copy link
Contributor Author

superseded by #367

@petrosagg petrosagg closed this May 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants